Conversation
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
a64b3e1 to
8df819a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
8df819a to
fa7f532
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@martian-engineering/[email protected]
Patch Changes
#185
ec74779Thanks @jalehman! - Fixlcm-tui doctorto detect third truncation marker format ([LCM fallback summary; truncated for context management]) and harden Claude CLI summarization with--system-promptflag and neutral working directory to prevent workspace contamination.#186
c796f7dThanks @jalehman! - Harden LCM summarization so provider auth failures no longer persist fallback summaries, and stop forcing explicit temperature overrides on summarizer requests.#182
954a2fdThanks @jalehman! - Improvelcm-tuisession browsing by showing stable session keys in the session list and conversation header, and align the session list columns so message counts and LCM metadata are easier to scan.#128
0f1a5d8Thanks @TSHOGX! - Honor custom API base URL overrides forlcm-tui rewrite,lcm-tui backfill, and interactive rewrite so TUI summarization can use configured provider proxies and non-default endpoints.